Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(main): [bot] release t8s-cluster:3.2.0 #591

Merged
merged 2 commits into from
Sep 27, 2023

Conversation

teutonet-bot
Copy link
Contributor

@teutonet-bot teutonet-bot commented Sep 25, 2023

🤖 I have created a release beep boop

3.2.0 (2023-09-26)

Features

  • t8s-cluster/workload-cluster: configure gpu time slicing (#575) (32fb616)

Bug Fixes

  • t8s-cluster/management-cluster: labels (#590) (de72cbc)

This PR was generated with Release Please. See documentation.

@teutonet-bot teutonet-bot changed the title chore(main): [bot] release t8s-cluster:3.1.1 chore(main): [bot] release t8s-cluster:3.2.0 Sep 26, 2023
@teutonet-bot teutonet-bot force-pushed the release-please--branches--main--components--t8s-cluster branch from 3ef4cdb to fa335b8 Compare September 26, 2023 08:04
@teutonet-bot
Copy link
Contributor Author

🤖 I have diffed this beep boop

"/$namespace/$kind/$name.yaml" for normal resources
"/$namespace/HelmRelease/$name/$namespace/$kind/$name.yaml" for HelmReleases <- this is recursive
'null' means it's either cluster-scoped or it's in the default namespace for the HelmRelease

charts/t8s-cluster/ci/artifacthub-values.yaml

charts/t8s-cluster/ci/cidrs-values.yaml

charts/t8s-cluster/ci/injectedCertificateAuthorities-values.yaml

charts/t8s-cluster/ci/securityGroups-values.yaml

charts/t8s-cluster/ci/calico-values.yaml has no changes

charts/t8s-cluster/ci/bastion-values.yaml

charts/t8s-cluster/values.yaml

charts/t8s-cluster/ci/gpu-flavor-values.yaml

@cwrau cwrau enabled auto-merge (squash) September 27, 2023 10:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants